Nways Manager for Windows NT Version 2.0 Installation Guide

Installing and Configuring Nways Manager

The main install program will start the Nways Manager install if the Nways Manager check box is checked on the main install dialog. You can also run the Nways Manager install program directly, as follows:

From the Windows NT Start Menu, Select Run....
Type f:\nwayswg\setup.exe, where f is the drive in which you inserted the CD-ROM.
Press Enter

On most install panels, pressing the F1 key will display the appropriate help. Follow the directions on each panel to install the product. The remainder of this chapter describes common problems to avoid and special considerations to be aware of when installing Nways Manager.

Upgrading to Nways Manager Version 2.0

In order to upgrade to Nways Manager Version 2.0 from an earlier version, you will have to uninstall the older version and then install the new version.

Installing the Products

When you install any of the products available in the Nways Manager package, a demonstration version of all products on the CD-ROM is installed, even if you did not purchase a license for the other programs. Any of those demonstration versions can be upgraded to the fully licensed version at any time. See "Demonstration Version" for more information.

Deployment Manager

To start Nways Deployment Manager from the NetView main menu, select Tools...>IBM Nways Java...>Open Deployment Manager.

Managing Licenses

As part of the installation process, you are asked whether or not you want to install a licensed product or a trial version of Nways Manager. If you elect to install a trial version of the product, all Nways Manager components will be installed with a demonstration license good for 60 days following installation. You can upgrade to a licensed version of Nways Manager at any time without losing your accumulated data.

If you select a licensed product, you will be prompted to enter your customer number and license key number, and then the number of nodes for which you have purchased a license.

Enter this information and click OK to continue the installation.

Upgrading Licenses

To upgrade from the demonstration version to the licensed version of Nways Manager, you must restart the installation program to install the license.
Note: No new code will be installed and your existing configuration will be preserved.

Increasing the Number of Licensed Nodes

If you have purchased a license to allow you to manage additional nodes, then use the following procedure to upgrade your license:

Start the installation process.
Select the radio button for Update number of nodes.
In the Update Licenses window, enter the total number of licensed nodes available. This is the number of pre-existing licensed nodes added to the new number of licensed nodes.
Click OK to save your changes.

Determining What Nodes to Monitor

Nways Manager determines what nodes to monitor by the contents of the file nwaysjma.ini. To remove nodes that you do not want to monitor and thus increase the number of other nodes you can monitor with your current license, you can edit this file and remove their entries. To edit the file, access the IBM Nways Manager for NT group and select Edit nwaysjma.ini.

To add nodes that you do want to monitor, edit the file and create entries for them. To do this, you must know their System Object Identifier (SYSOID).

A copy of this file is created in the c:nways/bin directory, where c: is the target drive of the installation. The file is created with the installation and is given the filename original.nwaysjma.ini. To revert to your original configuration, rename this file nwaysjma.ini.

Installing Java-based Distributed Intelligent Agent

The Java-based Distributed Intelligent Agent (DIA) is installed on remote workstations in your network to reduce the performance impact of performance polling. The DIA code is contained in the nways\java\dia subdirectory, where the nways is the directory where Nways Manager is installed. Refer to the README.TXT file in that directory for more information on installing the DIAs on PC and Unix-based workstations on your network.

DB2 Universal Database

Performance management for the Java-based device managers uses a Java Database Connectivity (JDBC)-compliant database. For your convenience, the Enterprise Edition of DB2 Universal database is provided.

You will need to create a database instance that can be accessed using JDBC by the device managers. The following steps show how to do this using DB2 (the concept is the same if you are using another JDBC-compliant database, but you will need to refer to that database's instructions):
Note: If you use IBM DB2 Universal Database V5, you need to retrieve and apply the Authorized Program Analysis Report (APAR) to avoid running out of virtual memory in the server process.
In the United States and Canada, telephone 1-800-237-5511 to request the DB2 APAR. Outside the country, contact your country support representative.

You will need to install the memory leak patch available at: http://www.software.ibm.com/data/db2/db2tech/indexsvc.html.

To install IBM DB2:

Insert the CD-ROM into the CD-ROM drive. The installation procedure begins automatically. If for any reason the automatic installation procedure does not start, go to the root directory on the CD-ROM and type setup.exe. Then follow the directions given in the installation procedure.
Unzip the JDBC drivers (found in DB2inst\sqllib\java\db2java.zip where DB2inst is the directory onto which DB2 was installed) into nways\java\websvr\code where nways is the directory into which Nways Manager was installed. You may have to retrieve an unzip program from the Internet to perform this task.
If when you installed the product you did not choose to automatically start DB2 on startup, start the server now by typing: db2start
Change to the directory nways\bin and run the command:
```
db2cmd CreateDatabase.bat -create
```
By default, a database will be created on the same disk that DB2 was installed. It is advised that this disk partition have at least 60 to 100 MB of free disk space. If you intend to store historical statistics for more than 20 devices over a period several weeks or longer, then you will need approximately 1 GB or more of available disk space.

To use DB2:

Start Nways Manager. (Start...Programs...IBM Nways Manager...Nways Manager).
Start the performance management configuration applet (Performance Configuration) and click on the tab labeled "Database."
- The performance management configuration applet can be launched by changing to nways\bin and executing the following command: dpadmin
- If you already have a JMA started, you can start the performance management configuration applet by selecting Performance Configuration from the navigation tree instead (Configuration " System " General " Performance " Configuration).
Click on the StartCollection button.

Clearing out the DB2 Database

After a period of use, it may be necessary to clear out the DB2 database. To clean out the database, change to the directory nways\bin, where nways is the directory into which Nways Manager was installed, and run the command: db2cmd CreateDatabase.bat -create

Potential Problems Connecting to a JDBC-enabled Database

If you encounter problems connecting to the JDBC-enabled database from Nways Manager, try the following solutions.

Message: Could not find JDBC driver classes. Closing connection.
Action:
Install or reinstall the JDBC drivers.

For DB2, unzip the JDBC drivers (found in DB2inst\sqllib\java\db2java.zip where DB2inst is the directory into which DB2 was installed) into nways\java\websvr\code, where nways is the directory into which Nways Manager was installed. You may have to retrieve an unzip program from the Internet to perform this task.
For other databases, refer to the documentation for those databases. The JDBC drivers must exist in the Nways classpath (nways\java\websvr\code, where nways is the directory into which Nways Manager was installed) to allow connection to the database.

Message: JDBC connect error. Check database URL and make sure your username and password are correct. Closing connection.
Action:

Check to make sure your database system and JDBC drivers are JDBC-compliant. The database must support ANSI-92 SQL.
Check the JDBC URL and make sure it is the one that the database manufacturer suggests you use. This can usually be found in the database documentation under a section dealing with running Java applications. If you are using a third-party driver, then the URL and driver name should be included with that driver. the default URL is given for the DB2 running locally.
Make sure you have created a database called IBMNMPDB.

If you are not using DB2, read your database documentation on how to do this.
If you are using DB2, change to the directory nways\bin, where nways is the directory into which Nways Manager was installed, and run the command: db2cmd CreateDatabase.bat -create

Make sure that the disk on which you have created the database has at least 60 to 100MB of space. The exact amount of space required depends on how much historical information will be stored
The following databases and JDBC drivers are known to be incompatible with Nways Manager and are not recommended:

Microsoft Access, JDBC-ODBC Bridge.

Accessing Java-based Management Applications from a Web Browser

There are three components involved in Web browser-based access to the Java-based management applications:

The Nways Manager Workstation: The Nways Manager maintains the Nways Manager web pages that are sent from the web server to the web browser clients.
The Web Server: The Web server provides the Nways Manager web pages to the web browser clients when requested. The web server does not need Java support, it sees the Nways Manager web pages as data files. It is recommended that the web server be located on the same workstation as the Nways Manager workstation.
The JDK 1.1.6-compliant Web Browser Client: The web browser client requests the Nways Manager web pages from the Web servers.
In order to utilize all the functions of Nways Nways Manager, you will need a JDK 1.1.6-compliant browser. However, to view the JMA help or the reports generated by the Java Performance Manager, you can use any web browser.

The Web Server

In order to make the Nways Manager web pages available to the web browser clients, you will need to associate the Nways Manager web pages with a logical directory name in your web server. Most web servers allow you to specify the logical directory name (for example, Nways) using its administration program. The Nways Manager web pages are located in nways\java\websvr on the Nways Manager, where nways is the directory in which you installed Nways Manager.

Settings

All Web Servers must be configured to communicate with the client on port 80, which is the default port in most Servers. The following sections define the required settings for some common Web Servers.

Apache Web Server

Add the following lines, in this order, to the file \Server_root\conf\srm.conf:

Alias \nways      "\Nways_root\java\websvr"
Alias \cgi\code   "\Nways_root\java\websvr\code"
ScriptAlias \cgi  "\Nways_root\java\websvr"

Where Server_root is the directory in which Apache Websvr is installed, and Nways_root is the directory where the Nways product is installed.

Netscape Web Server

Go to the server main page to verify that the server is on.
Select the Programs menu from the menu bar.
Select CGI File Type.
Select Yes to activate CGI as a file type.
Select Content Management from the menu bar.

Select Additional Document Directories, and add the following lines:

URL prefix: nways
Map To Directory: \Nways_root\java\websvr
 
URL prefix: cgi
Map To Directory: \Nways_root\java\websvr

Domino Web Server

Go to http://Machine/Frntpage.html, where Machine is the directory in which you installed the Domino Web Server.
Select Configuration and Administration Forms, which will take you to http://Machine/admin-bin/Cfgin/initial.
Select Request Routing, which will take you to http://Machine /admin-bin/Cfgin/mpfrule.

Add the following lines in this order:

Action     Request Template      Replacement File Path
------     ----------------      ---------------------
Pass       \nways\*           \Nways_root\java\websvr\*
Exec       \cgi\CgiLauncher*  \Nways_root\java\websvr\CgiLauncher*
Pass       \cgi\*             \Nways_root\java\websvr\*

The JDK 1.1.6-Compliant Web Browser

Java support comes with your browser.
Note: If you are using Microsoft Internet Explorer Version 4.x or 5.x, then you must update the Java Virtual Machine by selecting other options at the Web site: http://www.microsoft.com/windows/ie/download/default.asp.

For information on configuring your browser for use with Nways Manager, detailed instructions are contained in the file: nways\java\websvr\help\ibm.nways.subsys.webtoc.html. Nways is the directory where Nways Manager is installed.

After configuring your browser, you can access the Java-based management applications for your devices by specifying the URL for the Nways Manager HTML pages to the web browser.

Using Nways Manager with Dynamic IP Addresses

Java communications uses the IP host name and not the IP address, therefore both the client and server need the correct host names to which they are communicating. If the client is assigned an IP address dynamically, then you need to ensure that this IP address is associated with the client's IP host name. This process works correctly with NetView for NT using Dynamic Host Configuration Protocol (DHCP).
Note: HP OpenView Network Node Manager on Windows NT does not currently support DHCP.

If your client uses the PPP protocol to connect to the server, then the client will be dynamically assigned both an IP address and an IP host name. In this situation, Windows NT clients do not provide the correct IP host name to the Java applications running in the client. Hence, the Java-based applications will not provide the correct IP host name to the server, and the server will be unable to send asynchronous (unsolicited) events to the client. To correct this problem, change the IP host name on the client to the value "localhost" for the PPP connection's TCP/IP protocol. The Java code in the Windows NT client will then provide the server with the correct (dynamically assigned) IP host name.

To change your host's name to "localhost" for the TCP/IP protocol, perform the following steps:

For Windows NT 4.0

Select the Network Neighborhood icon on your desktop and click with the right mouse button.
In the popup menu that appears, select Properties at the bottom of the list.
Select the Protocols tab that appears at the top of the dialog.
Select the TCP/IP protocol in the list that is displayed, and click on the Properties... button at the bottom of the list.
Click on the DNS tab at the top of the next dialog that appears.
In the text entry field labeled "Host:," enter "localhost" (without quotes, all lowercase, with no spaces) as the new name of your machine.
Click on the OK button at the bottom of the two dialogs, and reboot the machine when instructed to do so.

Note that changing your host name in this manner will not modify the name of the computer in the Identification section of the Network Neighborhood properties, and will not change the name of the computer across dedicated LAN connections.

Accessing the Java-based Management Application Helps

The Java-based management applications use a Web browser to display their HTML help panels. The Nways Manager install program will attempt to locate your default browser by looking in the NT registry. If it finds one it recognizes, it will tell Nways Manager to use it.

If it cannot locate a browser it recognizes, then it will issue a warning message requiring you to specify the path in the nways\java\websvr\properties\BrowserApplet.txt. Specify the fully qualified name for the web browser on the "webBrowser.path=" line, where nways is the directory in which Nways Manager is installed.

About Device Configuration Programs

Some IBM networking devices include a configuration program. Nways Manager allows you to launch these configuration programs from the device's JMA.

In order to launch the configuration program from the JMA, Nways Manager must know the location of the configuration tool on the Nways Management Workstation. For configuration tools shipped after July 1998, this information is added to the program registry when the configuration tool is installed.

To locate older versions of configuration tools, Nways Manager includes the Config Tool Locator, which locates existing versions of configuration tools already installed on the Nways Management Workstation. You should run the Config Tool Locator when you install Nways Manager, and again after each installation of a configuration tool that originally shipped prior to July 1998.

To run the Config Tool Locator from the Start menu, select Programs " IBM Nways Manager " Config Tool Locator.

If the Config Tool Locator is unable to find a configuration tool that is loaded on the Nways Management workstation, you can add the location of the program to the registry using the following procedure:

Locate the correct configuration tool (cfg.exe or cfg.app file) on the path nways/java/fixcfg, and note the file size.
Check the Config Tool Locator's FixCfg.properties file to ensure that the file size of this configuration tool is unique.
Add a new entry to the FixCfg.properties file, using existing entries as models.
Rerun the Config Tool Locator.
Restart the JMA.

[ Top of Page | Previous Page | Next Page | Table of Contents ]

Message:	Could not find JDBC driver classes. Closing connection.
Action:	Install or reinstall the JDBC drivers. For DB2, unzip the JDBC drivers (found in DB2inst\sqllib\java\db2java.zip where DB2inst is the directory into which DB2 was installed) into nways\java\websvr\code, where nways is the directory into which Nways Manager was installed. You may have to retrieve an unzip program from the Internet to perform this task. For other databases, refer to the documentation for those databases. The JDBC drivers must exist in the Nways classpath (nways\java\websvr\code, where nways is the directory into which Nways Manager was installed) to allow connection to the database.
Message:	JDBC connect error. Check database URL and make sure your username and password are correct. Closing connection.
Action:	Check to make sure your database system and JDBC drivers are JDBC-compliant. The database must support ANSI-92 SQL. Check the JDBC URL and make sure it is the one that the database manufacturer suggests you use. This can usually be found in the database documentation under a section dealing with running Java applications. If you are using a third-party driver, then the URL and driver name should be included with that driver. the default URL is given for the DB2 running locally. Make sure you have created a database called IBMNMPDB. If you are not using DB2, read your database documentation on how to do this. If you are using DB2, change to the directory nways\bin, where nways is the directory into which Nways Manager was installed, and run the command: `db2cmd CreateDatabase.bat -create` Make sure that the disk on which you have created the database has at least 60 to 100MB of space. The exact amount of space required depends on how much historical information will be stored The following databases and JDBC drivers are known to be incompatible with Nways Manager and are not recommended: Microsoft Access, JDBC-ODBC Bridge.